Pressing a bare left arrow while attached now detaches back to the
dashboard when the agent's input box is (believed) empty, mirroring the
quick-escape UX of Claude-Code-style session managers. Ctrl+B d keeps
working unconditionally.

uam is a byte bridge and cannot see the agent's real input box, so
"empty" is approximated locally in the attach client's new stdinFilter
state machine: printables/tab and any forwarded escape sequence (which
may recall history or move through a menu) disarm the quick detach,
and Enter / bare Esc / Ctrl+C / Ctrl+U re-arm it. Modified arrows
(e.g. shift-left) and arrows inside a typed draft pass through
untouched. Bare Esc is detected via the end-of-chunk heuristic and
forwarded immediately so agent interrupts never lag.

Opt out with UAM_ATTACH_BACK_DETACH=0 for agents that bind a bare left
arrow themselves.

https://claude.ai/code/session_01CSfFSb43dMeARphdRnC1mE

Three gaps in the native backend's crash/logout story:

- The runtime dir defaulted to $XDG_RUNTIME_DIR/uam, which logind
  deletes when the user's last login session ends — not only on reboot.
  Detached hosts survive logout, so their sockets/state files vanished
  out from under them: uam lost track of running agents and resume
  would spawn duplicates. Default is now a per-UID directory under the
  system temp dir (the same reasoning behind tmux's /tmp/tmux-<uid>),
  verified to be a real directory owned by the current user since the
  parent is sticky and shared.

- State files persist host/child PIDs, so a stale file from a crashed
  host could match a recycled PID: List would report a dead session
  alive, and Kill's orphan escalation could signal an unrelated process
  group. State now records each process's kernel start time
  (/proc/<pid>/stat field 22) and every persisted-PID probe verifies it
  (procAliveWithStart), degrading to the plain signal-0 check where
  /proc is unavailable.

- Living in /tmp exposes the files to systemd-tmpfiles age-based
  cleanup; the host now refreshes its state file and socket mtimes
  every 6h so a long-idle session is never collected.

README documents the new location, the logout rationale, and the
loginctl enable-linger note for KillUserProcesses=yes distros.

https://claude.ai/code/session_01CSfFSb43dMeARphdRnC1mE

Resume previously relied on claude's --continue, whose "most recent
conversation in this cwd" heuristic resumes the wrong conversation when
several uam sessions share a directory.

Dispatch now seeds claude's own session id with the uam UUID via
--session-id, recorded in the store as provider_session_id (validated
against the UUID alphabet on load, since it is replayed as resume
argv). Resume targets that exact conversation with --resume <id>.

Seeding is gated on a per-binary capability probe (claude --help
advertising --session-id) so older claude releases — which reject
unknown flags at startup — keep the bare argv, and records without a
seeded id (pre-upgrade sessions, unsupported claude) keep the
--continue fallback.

Plumbing: adapter.Session/ResumeRequest gain ProviderSessionID, agents
gain an optional ProviderSession hook, and the service persists and
re-hydrates the id across refresh/resume. Codex stays on resume --last
(its CLI cannot preset session ids yet); copilot already resumed
exactly via --resume=<uam-id>.

https://claude.ai/code/session_01CSfFSb43dMeARphdRnC1mE

copilot already resumed exactly (--name <uam-id> at dispatch,
--resume=<uam-id> on resume — the pattern the claude change copied);
it now also records the seeded name as provider_session_id so the
store reflects what resume targets.

opencode supports exact resume natively (--session ses_...) but, like
codex, cannot preset the id at launch. Resume now targets the exact
session whenever a record carries a provider_session_id, falling back
to -c (project's most recent) otherwise.

The persisted-id allow-list widens from the UUID alphabet to the id
alphabets the providers actually use (alnum/underscore/dash, no
leading dash so a value can never parse as a flag).

https://claude.ai/code/session_01CSfFSb43dMeARphdRnC1mE

The ? overlay now lists the in-session keys (left-arrow quick detach
and the Ctrl+B d chord) so the attach UX is discoverable without the
README.

https://claude.ai/code/session_01CSfFSb43dMeARphdRnC1mE

setup-go installs the version from go.mod's go directive, so with
go 1.24.0 + toolchain go1.25.11 the CI golangci-lint was compiled with
Go 1.24 and refused to target the 1.25.11 toolchain ("Go language
version used to build golangci-lint is lower than the targeted Go
version"). Aligning the language directive with the 1.25 toolchain
makes setup-go install Go 1.25.x everywhere; the version check is
language-level, so build-go 1.25.x against toolchain 1.25.11 passes
(verified locally with golangci-lint built on go1.25.1).

https://claude.ai/code/session_01CSfFSb43dMeARphdRnC1mE